📘

Notes:

Errors return as standardized FDX error codes. See Errors.

Data calls can be validated against the provider-specific Mikomo users and sample responses for payload structure and actual data elements.

{
   "code": 401,
   "message": "Invalid input"
}

{
   "code": 602,
   "message": "Customer not authorized"
}

{
   "code": 701,
   "message": "Account not found"
}

{
   "code": 701,
   "message": "Account not found"
}

{
   "code": 401,
   "message": "Invalid Input"
}

{
   "code": 702,
   "message": "Invalid start or end date"
}

{
   "transactions": []
}

Some errors are difficult to replicate. For instance, there is no way for you to revoke an end-user’s consent via their bank’s app or website to test the errors that would result in your app. In these cases, we’ve made Mikomo users that when used, will supply certain error codes and messages. One such user is mikomo_601. When data is requested for this user, the result will always be a 601 error. See: Mikomo Error testing.

To test with these Mikomo users, go through the consent flow as usual to obtain an ID token. Then, any data call will result in the errors listed below.

{
   "code": 601,
   "message": "Customer not found"
}

{
   "code": 602,
   "message": "Customer not authorized"
}

{
   "code": 500,
   "message": "Internal server error"
}

{
   "code": 501,
   "message": "Subsystem unavailable"
}